Document management system user interfaces

ABSTRACT

Systems, methods, and software to provide document management system user interfaces to clients. Some embodiments include an intermediary server to provide document management system indexing data to a client in a form that is displayable within an existing client file browsing user interface, such as Windows Explorer.

CROSS REFERENCES

This application is a Continuation of U.S. application Ser. No. 13/401,577 filed Feb. 21, 2012, which is a Continuation of U.S. application Ser. No. 11/321,478, filed Dec. 29, 2015, now U.S. Pat. No. 8,122,070, issued Feb. 21, 2012, which is related to U.S. application Ser. No. 11/321,219 titled Document Management System User Interfaces filed on Dec. 29, 2005, and is also related to U.S. application Ser. No. 11/321,139 titled Document Management System User Interfaces filed on Dec. 29, 2005.

FIELD

The present subject matter relates to data processing and, more particularly, to document management system user interfaces.

BACKGROUND

Document management systems are becoming increasingly more common across organizations of all sizes. Organizations are utilizing document management systems as a tool to store documents of many types. Commonly, a single employee can generate several documents a day. Further, some documents, such as invoices or periodic account statements, are generated by automated process in large numbers and stored in the organizational document management system. Thus, the number of stored documents increases over time.

Documents are generally stored by document management systems in a linear fashion as documents are generated. File names typically are concise and are not descriptive of a document to an extent to allow easy searches. Thus, although some document management systems may use a folder/directory structure that might provide partial insight about a document, the full details, are not apparent at the individual document level.

Document management solutions generally involves end-user training in the new user interface, terminology and functionality available in a document management system; it might also require a software to be installed (a “thick-client”) on each of the users' boxes.

To organize documents, document management systems commonly include a database structure that stores metadata describing stored documents. To retrieve a document, a user generally utilizes a software component that must be loaded on the user's desktop. The user then utilizes that software component by entering data into a searching user interface regarding a needed document. This searching user interface of a document management system includes different fields in which to enter data descriptive of a document sought. After entering the information, a list of documents is retrieved and presented to the user in yet another user interface. However, the user may not have access to all of the documents displayed. Thus, document management systems, despite providing certain benefits, create additional support and training issues for organizations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a user interface diagram according to an example embodiment.

FIG. 2 is a schematic block diagram of a system according to an example embodiment.

FIG. 3 is a schematic block diagram of a system according to an example embodiment.

FIG. 4 is a block diagram of a method according to an example embodiment.

FIG. 5 is a block diagram of a method according to an example embodiment.

FIG. 6 is a block diagram of a method according to an example embodiment.

DETAILED DESCRIPTION

In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments in which the inventive subject matter may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice them, and it is to be understood that other embodiments may be utilized and that structural, logical, and electrical changes may be made without departing from the scope of the inventive subject matter. Such embodiments of the inventive subject matter may be referred to, individually and/or collectively, herein by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed.

The following description is, therefore, not to be taken in a limiting sense, and the scope of the inventive subject matter is defined by the appended claims.

The functions or algorithms described herein are implemented in hardware, software or a combination of software and hardware in one embodiment. The software comprises computer executable instructions stored on computer readable media such as memory or other type of storage devices. The term “computer readable media” is also used to represent carrier waves on which the software is transmitted. Further, such functions correspond to modules, which are software, hardware, firmware, or any combination thereof. Multiple functions are performed in one or more modules as desired, and the embodiments described are merely examples. The software is executed on a digital signal processor, ASIC, microprocessor, or other type of processor operating on a system, such as a personal computer, server, a router, or other device capable of processing data including network interconnection devices.

Some embodiments implement the functions in two or more specific interconnected hardware modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the exemplary process flow is applicable to software, firmware, and hardware implementations.

Various embodiments as described herein provide a user interface to a user of a document and record management system, such as Documentum available from EMC, Inc. of Hopkinton, Mass. In some such embodiments, such as the user interface example embodiment illustrated in FIG. 1, the user interface 100 provides the user a tree-view structure 102 from which to locate and access documents and records. This tree-view structure 102 allows the user to drill-down through the various levels of the tree-view structure to locate and access located documents and records. In some embodiments, documents can also be saved into the document management system using the user interface via a drag-and-drop action or a file save action of an application.

In some embodiments, this tree-view structure 102 is integrated within an operating system user interface without the need for any specific software to be deployed to the client. For example, the tree-view structure 102, can be displayed within a drive/folder/file user interface such as the Windows Explorer user interface of the Microsoft Windows operating system family or a file save interface of an application. The highest level of the tree view can be displayed and represented as a drive or network storage location 104 and the lower levels can be displayed as folders 106 within the drive or network storage location representation. Selection of a folder, such as folder 108, causes files, such as file 110, to be displayed within the user interface 100. Selection of the file 110 causes the operating system to open the file and display it to the user. In some embodiments, only documents and records a user is allowed to access are provided to a user. In some other embodiments, the user is only allowed to open records in a “read-only” mode.

In some embodiments, documents can be saved to folders 106 within the user interface 100. Some embodiments allow documents to be added to folders 106 via a drag-and-drop action and via a file save action from within an application. In some such embodiments, when a document is added to a folder, such as folder 108, the document is saved to the document management system with the same properties that define the folder. For example, if all documents within a folder are read-only, a document added to that folder will be stored in the document management system as read-only.

FIG. 2 is a schematic block diagram of a system 200 according to an example embodiment. The example system 200 includes a client 202, an intermediary server 210, and a document management system 220 interconnected via a network 230.

One example client 202 is in the form of a computer. The client 202 includes an operating system that controls client 202 operation. The client 202 can include a processing unit, memory, removable storage, and non-removable storage. The memory can include volatile memory and non-volatile memory. The client 202 can include or have access to a computing environment that includes—a variety of computer-readable media, such as volatile memory and non-volatile memory, removable storage and non-removable storage. Client 202 storage includes random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM) & electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD ROM), Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium capable of storing machine-readable instructions. The client 202 can also include or have access to a computing environment that includes input, output, and a communication connections. The client 202 can operate in a networked environment using a communication connection to connect to one or more remote computers, such as database servers 212, 222, 224, intermediary server 210, and other network resources. The communication connection can include a Local Area Network (LAN), a Wide Area Network (WAN) or other networks.

Machine-readable instructions stored on a machine-readable medium are executable by the processing unit of the client 202. A hard drive, CD-ROM, and RAM are some examples of articles including a machine-readable medium. The term “machine-readable medium” is also used to represent carrier waves on which the software is transmitted. For example, a computer program capable of providing a generic technique to perform access control check for data access and/or for doing an operation on one of the servers in a component object model (COM) based system according to the teachings of the present invention may be included on a CD-ROM and loaded from the CD-ROM to a hard drive. The machine-readable instructions allow the client 202 to provide generic access controls in a COM, TCP/IP, Server Message Block (“SMB”), or other protocol based, or protocol-hybrid, network system having multiple users and servers.

One example document management system 220 stores documents in a document storage module 224 and indexes data describing documents in a document indexing database 222. In some embodiments, the document management system is Documentum. The document management system 220 stores documents and makes them available on the network through a document management system 220 interface.

In some embodiments, document indexing data stored in the document indexing database is stored in a hierarchical fashion. The hierarchical fashion can be facilitated by a hierarchical database, a relational database with data arranged in a hierarchical fashion, or other database that facilitates storage of hierarchical data. One such hierarchical storage structure includes a client at the top of the hierarchy with client account types under the client. Under a client account type are one or more accounts of that type. Under a client account are documents associated with that account. This hierarchical structure facilitates display of the document indexing data in a tree-view structure, or other hierarchical data display. Data from the hierarchical structure can then be retrieved from the document indexing database by layer, one layer, multiple layers, or all layers at a time.

One example intermediary server 210 is a server that provides computing services on the network 230. Some such computing services include application hosting services, SMB file sharing services, Common Internet File System (“CIFS”) file sharing services, and other services and combinations of services. An example server 210 is JLAN Server version 3.4 available from Starlasoft.

In some embodiments, the intermediary server 210 services document management system 220 document indexing data requests from the client 202. The intermediary server 210, in some embodiments, accesses the document indexing data from the document indexing database 222 of the document management system 220. In other embodiments, the intermediary server 210 accesses the document indexing data from a document indexing database copy 212. After obtaining data requested by the client 202, the intermediary server, serves the requested data to the client 202. The document indexing data served to the client can be encoded according to a protocol, such as SMB, to cause the documents represented by the document indexing data to appear as documents available on a network drive.

In some embodiments, the client 202 receives the document indexing data from the intermediary server 210 and displays the data to a user within a user interface, such as user interface 100 of FIG. 1. In some embodiment, the user interface is a client 202 operating system user interface that displays the content of local or network drives, such as the Windows Explorer interface of Microsoft Windows operating systems.

In other embodiments, the user interface is presented within another client 202 program, such as Microsoft Outlook.

In some Outlook embodiments, such as embodiments utilizing Outlook 2002, the Integrated File Management (“IFM”) functionality is leveraged. The IFM functionality allows users to follow a specific link added to Outlook to navigate the Windows File System and network share drives using Outlook. The specific link is directed to the intermediary server 210. This provides seamless integration of Outlook to the document management system 220 via the intermediary server 210.

In some other Outlook embodiments, such as embodiments utilizing Outlook 2003 which no longer includes the IFM functionality with the standard product, a folder homepage is used. The folder homepage within Outlook links to an HTML page on a file server or a web server. This HTMI, page utilizes a component that provides browser based local file system access. In one embodiment, the component is ShellView Pack 6.1 available from Sky Software (www.ssware.com).

In some other Outlook embodiments, the Microsoft Outlook interface provides functionality through the use of controls, plugins, or Microsoft Outlook enhancements. Such enhancements provide the ability to users to drag and drop files to and from the document management system 220, perform document searches, open documents, and other actions.

A client 202 user, in some embodiments, can select a document representation derived from the document indexing data in the user interface and access the document. In some embodiments, the document is retrieved directly from the document management system 220, such as directly from the document storage module 224. In some embodiments, the document is retrieved directly from location the document management system causes the document to be stored, wherein the location the document is stored is identified in the document indexing data the client received from the intermediary server.

FIG. 3 is a schematic block diagram of a system 300 according to an example embodiment. The system 300 includes a client 302, a JLAN SMB server 310, and a Documentum Content Server 320. This embodiment simplifies the Documentum user interface while preserving valuable document management functionality. This embodiment further minimizes, and can even eliminate, the need to load client 302 with any thick-client applications.

This example embodiment is established by having the JLAN SMB server 310 on a remote machine acting as a file share while modification of the JLAN SMB server 310 provides interaction with the Documentum Content Server 320. The JLAN SMB server 310 is Java based and, thus, can run on any platform with a Java runtime environment. This embodiment can provide capabilities including document versioning, browsing, and access, among other capabilities control through a simple client 302 user interface. The end user experience, while interacting with the Documentum Content Server 320, is the same as using a standard file share user interface.

In some embodiments, the client 302 is a Microsoft Windows client that supports one of the SMB Dialects supported by the JLAN SMB server 310. In some embodiments, this is all that is need for the client 302 to be operative within the system 300.

The JLAN SMB server 310 is an extensible Java based SMB server and can be run on any of multiple platforms. In some embodiments, the JLAN SMB server 310 is implemented behind a load-balancing/fail-over switch to provide load-balancing and/or failover robustness between multiple JLAN SMB servers 310.

In a typical JLAN SMB server, file operations such as openFile, closeFile, readFile, writeFile, treeOpen, treeClose, and other operations are mapped to a file system. The methods behind these operations in the JLAN SMB server 310 of the present system 310 embodiment are modified to make corresponding calls to DocBroker associated with the Documentum Content Server 320 using Java based Documentum Foundation Class (“DFC”) 5.1.2 application programming interface 312. This results in a mapping between the file operations on the JLAN SMB server and the Documentum Content Server 320 and allows the client 302 to interact directly with Documentum.

The JLAN SMB server 310 accesses a document indexing database copy 316 via a database connectivity protocol, such as Java Data Base Connectivity (“JDBC”). The document indexing database copy 316 is a copy of all, or a portion of the document indexing database 322 associated with the Documentum Content Server 320. The JLAN SMB server 310 accesses the document indexing database 316 to retrieve document index data in response to a request from the client 302. This reduces latency in the document indexing database 322, can provide quicker client 302 access to the indexing data, and provides further benefits. The JLAN SMB server services the client 302 requests with the retrieved data.

In some embodiments, the document indexing data provided to the client 302 includes a handle to enable the client 302 to access documents represented in the retrieved document indexing data directly from a Documentum file store 324.

In some embodiments, a client 302 document index data request includes user, or client 302, data access credentials which are used by the SMB JLAN SMB server 310 to retrieve only documents the user or client 302 has access to. The use of these data access credentials, in some embodiments, further includes providing a user or the client 302 with read-only or other limited document privileges. These abilities provide functionality to embodiments that require documents to remain in a certain state, such as a quarterly statement maintained for historical purposes, or when certain users or clients do not have authority to perform certain actions with or to documents. In some embodiments, documents that are read-only, are displayed to on the client 302 under a root drive or folder in a tree-view structure indicating the documents are read-only. Further embodiments include displaying documents under a root drive or folder in a tree-view structure indicating the documents are editable. Folder and file names displayed on the client, in some such embodiments, provide context to documents displayed within folders and to actual documents via displayed file names. This quickly enables a client 302 user to visualize document properties.

A further result of providing the document index data to the client 302 through the JLAN SMB server 310 is that the client 302 can perform a document search using a standard client 302 operating system file search utility. In some embodiments, the client 302 includes a Microsoft Windows operating system and the document indexing data can be searched using the search utility within Windows Explorer.

FIG. 4 is a block diagram of a method 400 according to an example embodiment. The method 400 is an example method performed by a system that provides clients access to documents stored in a document management system through an intermediary server.

In some embodiments, the example method 400 includes storing documents within a document management system 402 and generating an index of documents stored within the document management system 404. The method 400 further includes receiving a document index data request from a client at an intermediary server 406 and servicing the document index data request from the intermediary server 408, wherein servicing the request includes serving data to be displayed within an operating system user interface. Some embodiments of the method 400 further include maintaining a copy of the document index in a document indexing database outside of the document management system and accessible to the intermediary server and retrieving requested document indexing data from the document indexing database.

Yet further embodiments of the method include receiving requested document indexing data at the client from the intermediary server 410 and accessing, by the client, a document stored in the document management system directly from the document management system 412. In some embodiments, accessing the document directly from the document management system 412 includes accessing the document from a location where the document management system causes the document to be stored.

FIG. 5 is a block diagram of a method 500 according to an example embodiment. The method 500 is an example method performed by an intermediary server, such as intermediary server 210 of FIG. 2 or JLAN SMB server 310 of FIG. 3.

The method 500 includes receiving a request for document management system document indexing data from a requestor over a network 502 and retrieving the document indexing data from a document management system document indexing database 504. The method 500 further includes encoding the retrieved data according to a protocol 506, wherein the encoded data appears as data available on a network drive, and sending the encoded data to the requestor over the network 508.

In some embodiments, receiving a request for document management system document indexing data 502 includes receiving user credential data. In some such embodiments retrieving the document indexing data 504 includes retrieving the document indexing data 502 of documents to which the user credentials provide access privileges.

In some embodiments of the method 500, the network is the Internet. In various other embodiments, the network include one or more networks such as a local area network, a wide area network, a global network, a system area network, the Internet, and a public switched telephone network interconnecting two or more computing resources, and other networks capable of transporting data between computing resources.

FIG. 6 is a block diagram of a method 600 according to an example embodiment. The method 600 is a method executed by a client to access documents stored in a document management system.

In some embodiments, the example method 600 includes receiving SMB data derived from a document management system index database 604 and displaying the SMB data within an operating system user interface that provides access to files stored in a networked environment 606. In some such embodiments, the SMB data provides a handle to a document stored by the document management system. In some embodiments, the method 600 includes requesting the SMB data 602. In some embodiments, the SMB data is requested 602 from the document management system. In other embodiments, the SMB data is requested 602 from a network resource other than the document management system, such as from an intermediary server.

It is emphasized that the Abstract is provided to comply with 37 C.F.R. §1.72(b) requiring an Abstract that will allow the reader to quickly ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.

In the foregoing Detailed Description, various features are grouped together in a single embodiment to streamline the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the invention require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

It will be readily understood to those skilled in the art that various other changes in the details, material, and arrangements of the parts and method stages which have been described and illustrated in order to explain the nature of this invention may be made without departing from the principles and scope of the invention as expressed in the subjoined claims. 

What is claimed is:
 1. A method comprising: receiving Server Message Block (SMB) data through an SMB intermediary server from a copy of a document indexing database, which is separate from a document management system and which is derived from a document management system index database that is stored within the document management system; reducing latency via receiving the SMB data through the SMB intermediary server from the document indexing database copy rather than by receiving the SMB data from the document management system index database; providing a fail-over robustness switch communicably connected to a number of SMB intermediary servers, which include the SMB intermediary server, the fail-over robustness switch being implemented in front of the SMB intermediary server; modifying a number of file operations in the SMB intermediary server to make a number of corresponding calls to a DocBroker; and displaying the SMB data within an operating system user interface that provides access to files stored in a networked environment, wherein the SMB data provides a handle to a document stored by the document management system, and wherein the handle includes a drag-and-drop action, and wherein the SMB data includes data stored in a hierarchy that enables a hierarchical display.
 2. The method of claim 1, the method further comprising requesting the SMB data.
 3. The method of claim 2, wherein requesting the SMB data includes providing a user data access credential, and wherein receiving the SMB data includes receiving only SMB data to which the user data access credentials provides access.
 4. The method of claim 3, wherein the SMB data to which the user data access credential provides access includes SMB data that is representative of documents to which the user data access credential provides read-only access.
 5. The method of claim 2, wherein requesting the SMB data comprises requesting the SMB data in a single hierarchical layer.
 6. The method of claim 1, wherein the SMB data is requested from a network resource other than the document management system.
 7. The method of claim 1, wherein displaying the SMB data within an operating system user interface comprises displaying the SMB data in an expandable and contractible tree-view display of data, and wherein the tree-view display is representative of document indexing within the document management system.
 8. A machine-readable storage medium, with instructions thereon which when processed, result in a machine: receiving SMB data through an SMB intermediary server from a copy of a document indexing database, which is separate from a document management system and which is derived from a document management system index database that is stored within the document management system; reducing latency via receiving the SMB data through the SMB intermediary server from the document indexing database copy rather than by receiving the SMB data from the document management system index database; providing a fail-over robustness switch communicably connected to a number of SMB intermediary servers, which include the SMB intermediary server, the fail-over robustness switch being implemented in front of the SMB intermediary server; modifying a number of file operations in the SMB intermediary server to make a number of corresponding calls to a DocBroker; and displaying the SMB data within an operating system user interface that provides access to files stored in a networked environment, wherein the SMB data provides a handle to a document stored by the document management system, and wherein the handle includes a drag-and-drop action, and wherein the SMB data includes data stored in a hierarchy that enables a hierarchical display.
 9. The machine-readable storage medium of claim 8, wherein the instructions when processed, further result in the machine requesting the SMB data.
 10. The machine-readable storage medium of claim 9, wherein requesting the SMB data includes providing a user data access credential, and wherein receiving the SMB data includes receiving only SMB data to which the user data access credentials provides access.
 11. The machine-readable storage medium of claim 10, wherein the SMB data to which the user data access credential provides access includes SMB data that is representative of documents to which the user data access credential provides read-only access.
 12. The machine-readable storage medium of claim 9, wherein requesting the SMB data comprises requesting the SMB data in a single hierarchical layer.
 13. The machine-readable storage medium of claim 8, wherein the SMB data is requested from a network resource other than the document management system.
 14. The machine-readable storage medium of claim 8, wherein displaying the SMB data within an operating system user interface comprises displaying the SMB data in an expandable and contractible tree-view display of data, and wherein the tree-view display is representative of document indexing within the document management system.
 15. A system comprising: a processor operable to execute instructions; a memory holding data including instructions operable on the processor to instantiate data processing modules, the data processing modules including: a data reception module to receive SMB data through an SMB intermediary server from a copy of a document indexing database, which is separate from a document management system, and which is derived from a document management system index database that is stored within the document management system; the data reception module to also reduce latency via receiving the SMB data through the SMB intermediary server from the document indexing database copy rather than by receiving the SMB data from the document management system index database; a fail-over robustness switch that is implemented in front of the Java SMB intermediary server and that is communicably connected to a number of SMB intermediary servers, which include the SMB intermediary server; a modification module to modify a number of file operations in the SMB intermediary server to make a number of corresponding calls to a DocBroker; and a data display module to display the SMB data within an operating system user interface that provides access to files stored in a networked environment, wherein the SMB data provides a handle to a document stored by the document management system, and wherein the handle includes a drag-and-drop action, and wherein the SMB data includes data stored in a hierarchy that enables a hierarchical display.
 16. The system of claim 15, further comprising a data request module to request the SMB data.
 17. The system of claim 16, wherein requesting the SMB data includes providing a user data access credential, and wherein receiving the SMB data includes receiving only SMB data to which the user data access credentials provides access.
 18. The system of claim 17, wherein the SMB data to which the user data access credential provides access includes SMB data that is representative of documents to which the user data access credential provides read-only access.
 19. The system of claim 16, wherein requesting the SMB data comprises requesting the SMB data in a single hierarchical layer.
 20. The system of claim 15, wherein displaying the SMB data within an operating system user interface comprises displaying the SMB data in an expandable and contractible tree-view display of data, and wherein the tree-view display is representative of document indexing within the document management system. 